System, method, and apparatus for using alternative numbers for routing voice calls and short messages in a communications network

ABSTRACT

A system, method and computer-readable medium for allowing the use of an alternative numbering plan for delivering short messages to mobile subscribers using the public mobile telephone network is provided. Users of an enterprise or other closed networks as well as users that are not part of a closed network may send short messages destined to members of an enterprise or closed network from their mobile or other devices associated with their subscription using an alternative enterprise directory number, such as the office number, instead of the mobile number, such that the alternative number will be presented at the destination device as the originating number. The recipient may respond to the message by addressing the response to the enterprise or closed network number, and the response may be delivered to the originator&#39;s mobile or other device associated with their subscription.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority of and is a continuation of U.S. Ser.No. 14/605,761, entitled SYSTEM, METHOD, AND APPARATUS FOR USINGALTERNATIVE NUMBERS FOR ROUTING VOICE CALLS AND SHORT MESSAGES IN ACOMMUNICATIONS NETWORK, filed on Jan. 26, 2015, now issued U.S. Pat. No.9,596,353, issued on Mar. 14, 2017, which is a continuation of U.S. Ser.No. 14/140,497, entitled SYSTEM, METHOD, AND APPARATUS FOR USINGALTERNATIVE NUMBERS FOR ROUTING VOICE CALLS AND SHORT MESSAGES IN ACOMMUNICATIONS NETWORK, filed on Dec. 25, 2013, now issued U.S. Pat. No.8,942,664, issued on Jan. 27, 2015, which is a continuation of U.S. Ser.No. 13/846,991, entitled SYSTEM AND METHOD Ser. No. 13/846,991, entitledSYSTEM, METHOD, AND APPARATUS FOR USING ALTERNATIVE NUMBERS FOR ROUTINGVOICE CALLS AND SHORT MESSAGES IN A COMMUNICATIONS NETWORK, filed onMar. 19, 2013, now issued U.S. Pat. No. 8,634,800, issued on Jan. 21,2014, which is a continuation of U.S. Ser. No. 13/307,112, entitledSYSTEM, METHOD, AND APPARATUS FOR USING ALTERNATIVE NUMBERS FOR ROUTINGVOICE CALLS AND SHORT MESSAGES IN A COMMUNICATIONS NETWORK, filed onNov. 30, 2011, now issued U.S. Pat. No. 8,412,241, issued on Apr. 2,2013, which is a continuation of U.S. Ser. No. 11/750,756, entitledSYSTEM, METHOD, AND APPARATUS FOR USING ALTERNATIVE NUMBERS FOR ROUTINGVOICE CALLS AND SHORT MESSAGES IN A COMMUNICATIONS NETWORK, filed on May18, 2007, now issued U.S. Pat. No. 8,086,254, issued on Dec. 27, 2011,incorporated herein by reference in their entirety.

FIELD OF THE INVENTION

The present disclosure relates to telecommunications and, moreparticularly, to telecommunications including voice calls and shortmessage service, enterprise servers, wireless communications, and theinteroperability of communication technologies.

BACKGROUND

Corporations are increasingly relying on the use of cellular technologyby their employees, yet enterprises do not have adequate means tocontrol cellular service in terms of costs, Quality of Service, andcorporate monitoring. This is because cellular service hasconventionally been controlled by wireless carrier networks and managedindependently of, and with no connectivity to, the enterprise voice anddata networks.

Enterprises today control their enterprise fixed voice and data networksby deployment of private branch exchanges (PBXs). The enterprise may ownand manage PBXs within each branch and between branch offices. Theenterprise may also own and manage their own data networks and corporatelocal area network (LAN)/wide area network (WAN). Bulk voice minutes anddata capacity may be purchased from land-line carriers, or from otherproviders that have purchased bulk minutes and data capacity fromcarriers. The purchased capacity may then be used to connect branchoffices using public IP Network providers, e.g., MCI, Sprint, L3, etc.,for Data and Voice over IP (VoIP). Heretofore, no mechanisms have beenprovided to extend the enterprise fixed voice and data networks paradigmto cellular services.

SUMMARY OF THE INVENTION

Embodiments disclosed herein provide mechanisms for enabling the use ofan alternative numbering plan for delivering voice calls and shortmessages to mobile subscribers using the public mobile telephonenetwork. Using the methods described herein, users of an enterprise orother closed networks as well as users that are not part of a closednetwork may send short messages destined to members of an enterprise orclosed network from their mobile or other devices associated with theirsubscription using an alternative enterprise directory number. Thealternative enterprise directory number may comprise an office number ofa land-line telephony device. In accordance with embodiments, thealternative enterprise directory number, rather than the mobile number,will be presented at the destination device as the originating number.The recipient can respond to the message by addressing the response tothe enterprise or closed network number and it will be delivered to theoriginator's mobile or other devices associated with their subscription.The disclosure additionally addresses alternative routing of voice callsdirected to the enterprise or closed network numbers such as when thepublic landline networks is not available during an emergency, as wellas addressing potential routing conflicts between the public mobile andland-line networks.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the followingdetailed description when read with the accompanying figures, in which:

FIG. 1 is a diagrammatic representation of a network architecture inwhich embodiments disclosed herein may be implemented;

FIG. 2 is a diagrammatic representation of another network architecturefeaturing split call control in accordance with an embodiment;

FIG. 3 is a diagrammatic representation of an embodiment of gatewayserver implemented in accordance with an embodiment;

FIG. 4A is a diagrammatic representation of an exemplary HLR record thatdefines a subscriber profile implemented in accordance with anembodiment;

FIG. 4B is a diagrammatic representation of an exemplary HLR dummyrecord that may be associated with a land-line telephony device thatfacilitates one number services implemented in accordance with anembodiment;

FIG. 5 is a simplified diagrammatic representation of an exemplary SMSmessage format implemented in accordance with an embodiment;

FIGS. 6A-9C are diagrammatic representations depicting signaling flowsof an SMS transmission and representative SMS messages in a networksystem implementing one number servicing in accordance with aembodiments;

FIG. 10 is a diagrammatic representation depicting a signaling flow forhandling of mobile originations for voice calls to an enterprise numberwhich is provisioned in a mobile network HLR in accordance with anembodiment;

FIG. 11 is a flowchart of exemplary SMS message processing as may beimplemented by an enterprise gateway server that facilitates one numberservice in accordance with an embodiment; and

FIG. 12 is a diagrammatic representation depicting a signaling flow forhandling of mobile originations for voice calls to an enterprise numberwhich is provisioned in a mobile network HLR in accordance with anembodiment.

DETAILED DESCRIPTION

It is to be understood that the following disclosure provides manydifferent embodiments, or examples, for implementing different featuresof various embodiments. Specific examples of components and arrangementsare described below to simplify the present disclosure. These are, ofcourse, merely examples and are not intended to be limiting. Inaddition, the present disclosure may repeat reference numerals and/orletters in the various examples. This repetition is for the purpose ofsimplicity and clarity and does not in itself dictate a relationshipbetween the various embodiments and/or configurations discussed.

With the ubiquity of cellular communication devices, it is desirable toseamlessly integrate public wireless voice and data networks withenterprise networks. More particularly, it is desirable to provideenterprise cellular solutions that may operate in conjunction withpublic network infrastructure. While enterprise-provisioned cellularservices may provide enhanced personnel communications and connectivity,the variety of user communication devices, e.g., land-line phones,cellular phones, personal digital assistants, and the like, mayintroduce challenges for providing timely delivery of communicationservices. For example, enterprise personnel may be assigned numerouscommunication devices, such as a land-line phone for use when theemployee is at a work station or office, and a cellular phone or apersonal digital assistant when the employee is away from the officeeither at other locations in the enterprise or outside the enterprisepremises. Because the employee may be equipped with communicationdevices best suited for use when the employee is at a particularlocation as well as a mobile communication device for use when theemployee is on the move, persons attempting to contact the employee maynot be aware of the best means for communication with the employee at aparticular time.

In accordance with the present disclosure, the enterprise is able toequally extend the enterprise fixed voice and data networks paradigm tocellular services by connecting the public wireless voice and datanetwork with the enterprise. A gateway server inter-connects thecarrier's Mobile Switching Center (MSC) that manages cellular voicetraffic as well as the carrier's Serving GPRS Support Node (SGSN) thatmanages cellular data traffic, with the enterprise's voice and datanetwork. In accordance with a particular embodiment, a one numberservice feature may be provided that allows the enterprise subscribersor personnel the use of multiple communication devices with a singleenterprise directory number. An enterprise member may be assigned aland-line phone and a cellular telephone and may be only aware of theenterprise directory number of the land-line phone. Likewise, colleaguesor personal contacts may only be provided with the enterprise member'sland-line phone number yet may advantageously contact the enterprisemember on both the enterprise member's land-line phone and cellulartelephone using the land-line phone number assigned to the enterprisemember. More particularly, an enterprise member may originate shortmessage service (SMS) messages from the mobile terminal assigned to themember. The MSISDN number of the originating mobile terminal may bereplaced with the land-line phone number assigned to the member when theSMS message is in transit. Accordingly, a destination user that receivesthe SMS message will be presented with the land-line number of theoriginating member. In a similar manner, a contact of the enterprisemember may originate an SMS message to the member using the member'sland-line enterprise directory number as the destination number of theSMS message. The enterprise land-line number entered as the destinationnumber may be replaced with the land-line phone number assigned to themember when the SMS message is in transit. Accordingly, the enterprisemember may then receive the SMS message on the member's mobile terminalalthough the SMS message was originally addressed to the land-line phonenumber.

FIG. 1 is a diagrammatic representation of a network 100 architecture inwhich embodiments disclosed herein may be implemented. Network 100 mayinclude a cellular network system 110, such as a Global System forMobile (GSM) Communications network, a code division multiple access(CDMA) network, a mobile network utilizing IMT-2000, or another suitablemobile network. Cellular network system 110 generally includes aSwitching System (SS) 120 and a Base Station System (BSS) 130. In theexamples provided herein, mobile network architecture components aremade with reference to the GSM, the most popular standard for mobilephones in the world. GSM is both an air interface and networkingprotocol. The most popular alternative combines the Code DivisionMultiple Access (CDMA) air interface protocol and the ANSI-41 Networkingprotocol.

Each of SS 120 and BSS 130 contain a number of functional units wellunderstood by those skilled in the art, and a detailed explanation ofthe various components is unnecessary. Nevertheless, a cursory review ofvarious components is provided. SS 120 contains a Mobile servicesSwitching Center (MSC) 122, a Home Location Register (HLR) 124, and aVisitor Location Register (VLR) 126. MSCs carry out switching functionsand manage the communications between mobile phones and the PublicSwitched Telephone Network (PSTN) 190. HLR 124 comprises the centraldatabase that contains details of each mobile phone subscriber that isauthorized to use the cellular core network. VLR 126 comprises adatabase which stores information about all the mobiles terminals thatare currently serviced by the associated MSC (MSC 122 in the presentexample). VLR 126 stores various information regarding the mobileterminals, such as the current location area identity that specifies aparticular base station controller (BSC) that the mobile station iscurrently serviced by.

Various other sub-systems or functional modules may, and typically are,included in SS 120, such as an Authentication Center, an EquipmentIdentity Register, or various other functions. A serving general packetradio service (GPRS) support node (SGSN) 128 may be included in cellularnetwork system 110 to facilitate provisioning of packet services to andfrom mobile terminals in network system 110. GPRS provides mobilitymanagement, session management and transport for Internet Protocolpacket services in GSM cellular packet networks.

As is understood, various GPRS infrastructure may be included in networksystem 110 to provide packet services to mobile terminals, and only SGSN128 of the GPRS core network is depicted to simplify the discussion ofembodiments disclosed herein. In general, a gateway GPRS support nodemay interface the GPRS backbone with an external packet network, such asthe Internet.

SGSN 128 may interface with various subsystem of network system 110. Forexample, SGSN 128 may have a Gs interface with MSC 122 and VLR 126 thatfacilitates paging and station availability notification when performingdata transfers. SGSN 128 may additionally have a Gr interface with HLR124 through which messaging may be performed, for example, over theMobile Application Part protocol. SGSN 128 may additionally have a Gbinterface with packet control unit (PCU) (not shown) of BSS 130 thatfacilitates connection of BSS 130 with SGSN 128.

Network system 110 may also include a signaling system, such as a SS7network 160. SS7 network 160 provides a set of telephony signalingprotocols which are used to set up the vast majority of the world's PSTNtelephone calls. SS7 network 160 is also used in cellular networks, suchas GSM and UMTS, for circuit switched voice and packet-switched dataapplications. As is understood, SS7 network 160 includes varioussignaling nodes, such as any number of service control points (SCPs)162, signal transfer points (STPs) 164, and service switching points(SSPs) 166.

BSS 130 contains a Base Station Controller (BSC) 132 that may be incommunication with and in control of a plurality of Base TransceiverStations (BTSs) 134-138. Each individual BTS 134-138 under the controlof a given BSC 132 may define a radio cell operating on a set of radiochannels thereby providing service to a Mobile Terminal (MT) 140.

Network system 110 may also include a short message service center(SMSC) 144 adapted to deliver short message service (SMS) messages tomobile terminals. When an SMS message is sent to a user, the SMS messageis stored in SMSC 144 which delivers it to the destination mobileterminal when the destination mobile terminal is available. As is known,the SMS message may be delivered via a control channel, e.g., a cellbroadcast control channel, or bearer channel.

Network 100 may include an enterprise network 150, such as a switchedEthernet, that interconnects various network nodes via various networkinfrastructure, such as hubs and switches. In the illustrative example,enterprise network 150 includes various client nodes, such as desktopclients 152 and 153, land-line Internet Protocol (IP) telephones154-155, and an IP private branch exchange (PBX) 158 which carries callsover IP, e.g., via voice over IP (VoIP). Enterprise network 150 mayinterface with the PSTN 190 via a router 172 disposed at the enterprise.

Likewise, enterprise network 150 may interface with cellular networksystem 110 via routers 170 and 172. It is understood that enterprisenetwork 150 may, and typically does, include hundreds or thousands ofclient devices and networking nodes, and the architecture depicted inFIG. 1 is greatly simplified to facilitate a discussion of embodimentsdisclosed herein.

In accordance with an embodiment, an enterprise gateway server 180 maybe deployed in enterprise network 150 that is adapted to inter-connectthe mobile network's MSC 122 that manages cellular voice traffic as wellas the SGSN 128 that manages cellular data traffic. Enterprise gatewayserver 180 may include or interface with a softswitch media gateway 181.From an IT organization perspective, gateway server 180 appears as anextension to PBX 158. To cellular network system 110, gateway server 180appears as a standard in-network endpoint for delivering calls. To PBX158, gateway server 180 appears as a set of standard PBX endpoints (e.g.deskphones, or IP clients). Gateway server 180 mediates between the twodisparate sets of network protocols and state machines.

Gateway server 180 may include the network functions for both voice(gateway MSC) and data (gateway GPRS Support Node or Home Agent), VoIPcapability for interconnecting mobile network 110 with enterprisenetwork 150 thereby eliminating PSTN interconnect charges, a billinggateway, and a next-generation Network Services gateway that enablesthird party value added services for the enterprise, such as mobilephone activation/de-activation, corporate directory integration based onIMS (IP Multimedia Subsystem), or other services. Gateway server 180 mayalso include the element management subsystem (EMS) and a servicemanagement subsystem for the operational support system (OSS).

In the example depicted in FIG. 1, call control may be managed by theenterprise in which the gateway server is located. In thisimplementation, the gateway server interfaces with cellular networksystem 110 nodes supporting SS7 and SIP or other messaging with thecarrier network, and the cellular network must be able to addressgateway server 180 in order to send and receive messages.

In another embodiment, call control may be split or partitioned betweenthe carrier and enterprise networks as depicted in the networkconfiguration 200 of FIG. 2. In this implementation, an enterprisegateway server (GS-E) 182 interacts with a carrier gateway server (GS-C)180 deployed in the carrier network. The connection between GS-E 182 andGS-C 180 may be made over SIP or other protocols. This configuration mayenable cellular network system 110 to have a central point of controlfor interacting with multiple enterprises, and may not require the useof SS7 messaging to the enterprise. Rather, it is possible to have asecure IP connection supporting SIP. This is also useful for offering aCentrex solution for interconnecting with a carrier-hosted PBX, or forinterconnecting a carrier-hosted gateway server with enterprise-hostedPBX 158 systems. GS-C 180 may support an SS7 point code multiplexer inwhich only one or two point codes are needed to address all enterprisessince GS-C 180 can identify for which enterprise the message isintended. In the illustrative example, GS-C 180 has a point code “PointCode_(A)” and softswitch media gateway 181 has a point code “PointCode_(B)”. GS-E 182 may be adapted to provision GS-C 180 automaticallyover the IP interface to manage subscribers, e.g., to add new pilotdirectory numbers (DNs) for new subscribers. In this case, originatingand terminating triggers used in cellular network system 110 for routingcalls to GS-C 180 can add identifying information of the specificenterprise in the triggering messages. Alternatively, GS-C 180 mayidentify the enterprise based on the calling party information.

In the illustrative examples provided herein, Party A and Party B areboth members of enterprise network 150. Party A is assigned a mobileterminal 140 having an MSISDN of 1-972-444-1001, and Party B is assigneda mobile terminal 141 having an MSISDN of 1-972-444-1002. Party A isassigned enterprise land-line telephony device 154 having an enterprisedirectory number of 1-972-555-2001, and Party B is assigned enterpriseland-line telephony device 155 having an enterprise directory number of1-972-555-2002. Additionally, Party A and Party B are assigned arespective desktop client 152 and 153. In some examples, reference ismade to another mobile terminal user, Party C, that is not a member ofenterprise network 150. In the illustrative example, Party C is assigneda mobile terminal 142 having an MSISDN of 1-214-777-7777.

GS-E 182 may include or interface with an Enterprise member database 190that stores records or profiles that define services for members ofenterprise network 150. Enterprise member database 190 may facilitateone number servicing implemented in accordance with embodiments byassociating a land-line telephony device and a mobile terminal commonlyassigned to a particular enterprise member. For example, enterprisemember database 190 may include a record 190 a allocated for Party Athat is a member of enterprise network. In the illustrative example,record 190 a includes a Land-line field that stores an enterprisedirectory number of a land-line telephony device 154 assigned to PartyA, and an MSISDN field that stores a directory number of mobile terminal140 assigned to Party A. In this manner, the land-line number and thedirectory number (MSISDN) of the mobile terminal of the user Party A areassociated with one another. In a similar manner, Party B that is amember of enterprise network 150 has a record 190 b that associates theenterprise directory number of an enterprise telephony device 155assigned to Party B with the mobile number of mobile terminal 141assigned to Party B.

In general, exemplary processing routines described herein are providedwith reference to a split call control configuration featuring bothenterprise and carrier gateway servers. However, embodiments disclosedherein are not limited to such a configuration and may be similarlyimplemented in a system deploying a gateway server in the enterprise asdepicted in FIG. 1 as will be apparent to those skilled in the art.

FIG. 3 is a diagrammatic representation of an embodiment of gatewayserver 180 depicted in FIG. 1. Gateway server 180 includes hardware andan operating system 310, such as an instance of the Unix operatingsystem. Various protocol stacks may be deployed and run by the gatewayserver. In the illustrative example, the gateway server includes anetwork layer 320, such as an Internet Protocol layer. Transportlayer(s), such as user datagram protocol (UDP) 322, transport controlprotocol (TCP) layer 324, and stream control transmission protocol(SCTP) layer 326, may be included in the gateway server and interfacewith the lower network layer 320 and applications above the transportlayer. Application layers that interface with lower transport layers mayinclude a session initiation protocol (SIP) layer 328 for creating,modifying, and terminating sessions with one or more devices and H.323compliant layer 330 for provisioning of communication sessions over apacket network. The gateway server additionally includes mobilenetworking protocol layers, such as ANSI-41 and GSM layers 332. Advancedintelligent network and wireless intelligent network capabilities may beprovided by the gateway server via, for example, a CustomizedApplications for Mobile networks Enhanced Logic (CAMEL) layer 334 and/ora wireless intelligent network (WIN) layer that allows an operator todefine services over and above standard services provided by the GSMstandards. The gateway server may include any variety of applications,such as H.323 communication application 340, an element managementsubsystem 342, a short message service system 344, BGW 346, and anapplication programming interface 348. Additionally, the gateway servermay include a session initiation protocol layer 350, gateway GPRSsupport node home agent application 352, gateway mobile servicesswitching center 354, session control protocol 356, and home locationregister/home subscriber server application 358. Various otherapplications may be included in addition to, or in lieu of, any one ormore of the depicted applications.

The gateway server enables the enterprise to manage and control itscellular service in addition to providing a significant overall costreduction for telecommunications. Moreover, the gateway server includesan overall platform and architecture for improved and integratedwireless enterprise solutions and facilitates convergence between theenterprise's cellular and Voice over IP (Internet Protocol)infrastructure.

The gateway server leverages the benefits of Voice over IP with cellularto extend the cellular network into the enterprise. The gateway serveraddresses both cellular voice and data, and is a networking solutionthat works together with the enterprise's existing PBX, performingmobile call control functions (routing and services).

Additionally, the gateway server bridges the enterprise PBX and publiccellular environments to enable telecom applications for the cellularuser, such as short-code dialing (e.g. 4 and 5-digit dialing), onenumber service (one phone number for the land-line and cellular phone),and single voice mail box that services both a user's land-line andcellular telephone. The gateway server enables the enterprise toleverage existing telecom assets for cellular use (e.g., least-costrouting over a corporation's VoIP or leased-lines network for discountedlong distance; use of existing PBX voicemail system).

The gateway server is an application platform for deploying mobile ITapplications. Either the enterprise IT department or a SystemsIntegrator may develop and integrate specific applications to interfacewith the corporation's cellular devices. For example, the enterprise canchoose to replace the desk phone of an office employee with aninexpensive mobile phone. For this employee, when they ‘badge-out’ ofthe building at the end of the day, the enterprise security budgingsystem can be used to inform the gateway server to de-activate themobile phone, until the employee returns to the office and ‘badges-in’the next morning. Alternatively, the gateway server can track and recordthe calls made outside the office hours, and enable the enterprise tocharge them to the business, to the employee, or record them as acorporate benefit.

The gateway server may be a software-only solution that can execute onstandard, inexpensive Linux platforms. The gateway server may comprise amobile core network (for call handling and routing) and services network(voice and data services such as PBX-based short code dialing,voicemail, conference calling, VPN, etc.) components. It may beappropriately scaled down to the smaller subscriber base of adecentralized large enterprise, in the order of hundreds to severalthousand subscribers, compared with carrier systems that manage manymillions of “centralized” subscribers. The gateway server is designed tobe managed and maintained by the same IT group that currently managesthe enterprise's PBX system.

In accordance with an embodiment, one number service provides for calltermination with multiple terminals, e.g., a land-line phone and acellular telephone. An enterprise employee may be assigned a land-linephone and a cellular telephone and may use a single destination numberfor either device for receiving and originating telephone calls and dataservice. Accordingly, users attempting to contact an enterprise employeeneed only have a single phone number assigned to the employee for makinga phone call to either the employee's land-line phone or cellulartelephone. In accordance with a particular embodiment, short messageservice (SMS) messages may be originated by an enterprise employee froma cellular telephone assigned thereto, and the SMS message mayultimately be delivered to a destination device with the land-lineenterprise directory number associated with the originating employeeincluded in the SMS as the origination number. Thus, an enterpriseemployee originating a SMS message from a cellular phone may have theSMS message delivered to the target device whereupon the SMS message isdisplayed as originating from the enterprise employee land-line phonenumber. In a similar manner, a person originating an SMS may enter theland-line number of an enterprise employee, and the MSISDN assigned tothe cell phone of the enterprise employee may be substituted for theland-line number by the gateway server (either the GS-E or GS-C) andsubsequently delivered to the enterprise employee's cell phone. In thismanner, a user may be only aware of the employee's land-line enterprisedirectory number but may advantageously deliver SMS messages to theenterprise employee's cell phone as will be described more fullyhereinbelow.

FIG. 4A is a diagrammatic representation of an exemplary HLR record 400that defines a subscriber profile implemented in accordance with anembodiment. In general, HLR 124 may, and typically does, includethousands of records each associated with a particular mobilesubscriber. Each HLR record includes details of a respective subscriberauthorized to use cellular network 110. In the illustrative example, HLRrecord 400 is representative of an HLR record allocated for Party A'smobile terminal (mobile terminal 140 in FIGS. 1 and 2) in the depictedFigures.

HLR record 400 comprises a plurality of fields 402-420 which each storeinformation regarding a particular mobile terminal assigned to asubscriber of cellular network 110. Fields 402-420 have respectivelabels of “IMSI”, “MSISDN”, “Voice”, “SMS.”, “GPRS_Settings”, “VLR_ID”“SGSN_ID” “SMS-CSI”, “SMSC_Number,” and “MSC_ID”. A particular field,e.g., IMSI field 402 and MSISDN field 404, may be designated as a keyfield and each respective data element is unique within key fields402-404.

In the illustrative example, IMSI field 402 maintains an InternationalMobile Subscriber Identity (IMSI) stored in the subscriber identitymodule (SIM) of the mobile terminal for which HLR record 400 isallocated. The IMSI comprises a unique number associated with aparticular mobile terminal. The IMSI is typically a 15-digit numberhaving the first 3 digits that specify a mobile country code followed bya 3-digit mobile network code associated with cellular network 110 towhich the mobile terminal is registered. The remaining digits maycomprise a mobile subscriber identification number (MSIN) assigned tothe customer (Party A in the present example) associated with the mobileterminal. In the illustrative example, the IMSI has a value of“3101501234567890” assigned thereto.

A mobile subscriber ISDN (MSISDN) field 404 may store the MSISDN, ordirectory number, assigned to the mobile terminal for which record 400is allocated. In the illustrative example, the MSISDN field 404specifies a MSISDN number of “19724441001”, that is the directory numberassigned to mobile terminal 140. Each of IMSI field 402 and MSISDN field404 may be used as primary keys for accessing HLR record 400.

HLR record 400 may record various subscription services for the mobileterminal. In the illustrative example, various service fields may havevalues that indicate whether the subscriber for which the HLR record isallocated is authorized to use a particular service. In the presentexample, Voice field 406 has a value of true (T) that indicates thatassociated subscriber is authorized for voice service, and SMS field 408has a value of true that indicates the mobile terminal is authorized tooriginate and receive SMS messages. Various other service fields may,and typically are, included in HLR 400 that each specify any one or moreof various subscription services, such as call waiting, call forwarding,and the like.

A GPRS_Settings field 410 may specify whether the mobile terminal has aGPRS subscription and settings thereof. For instance, GPRS_Settingsfield 410 may have a false setting or have another indicator thatspecifies the mobile terminal associated with HLR record 400 does nothave a valid GPRS subscription. In the event that the mobile terminalhas a GPRS subscription, GPRS_Settings field 410 may specify a serviceclass. In the illustrative example, GPRS_Settings field 410 specifiesthat the associated mobile terminal has a GPRS subscription with aservice setting of “Class_10”.

VLR_ID field 412 may specify the current VLR servicing the mobileterminal associated with HLR record 400. In the present example, VLR_IDfield 412 indicates the mobile terminal is being serviced by a VLRhaving an ID of VLR₁. In a similar manner, SGSN_ID field 414 may specifythe current SGSN servicing the mobile terminal associated with HLRrecord 400. In the present example, SGSN_ID field 414 indicates themobile terminal is being serviced by an SGSN having an ID of SGSN₁.

An Short Message Service-Customized Applications for Mobile networksEnhanced Logic (CAMEL) Subscription Information (SMS-CSI) field 416 maycontain trigger information required to invoke CAMEL Service Logic forMobile Originating Short Message Submissions. In the illustrativeexample, the trigger information maintained in SMS-CSI field 416 isdiagrammatically represented as “trigger_info”. A short message servicecenter (SMSC) Number field 418 may include an identifier, e.g., an SS7point code, assigned to an SMSC that is to service the associatedsubscriber. In the illustrative example, SMSC_Number field 418 has avalue of Point Code, assigned to SMSC 144 depicted in FIGS. 1 and 2. AnMSC_ID field 420 may include an identifier, e.g., a point code, of theMSC currently, or most recently, servicing the mobile terminalassociated with HLR record 400. In the present example, the point codeof the MSC specified by MSC_ID field is represented as “Point Code_(x)”.

To facilitate provisioning of one number service, the HLR mayadditionally include a “dummy” profile assigned to a land-line telephonydevice to facilitate one number voice and data services. FIG. 4B is adiagrammatic representation of an exemplary HLR record 450 that may beassociated with a particular enterprise user that facilitates one numbervoice and data services. HLR dummy record 450 is assigned to a land-linetelephony device assigned to an enterprise subscriber and is distinctfrom an HLR record assigned to the subscriber's mobile terminal. In theillustrative example, HLR record 450 is allocated for Party A that is amember of the enterprise network and is associated with Party A'senterprise land-line telephony device 154 depicted in FIGS. 1 and 2. HLRrecord 450 may include an IMSI field 452 that may be nulled or assignedan identifier that indicates that no IMSI is associated with thetelephony device for which HLR record 450 is allocated. An MSISDN field454 may have a land-line number assigned thereto for associating dummyHLR record 450 with a land-line telephony device. In the presentexample, MSISDN field 454 has a value of 19725552001, that is theenterprise directory number of the land-line device 154 assigned toParty A in FIGS. 1 and 2. HLR record 450 may include various servicefields that indicate validity, invalidity, or other subscriptioncharacteristics of various services. In the present dummy HLR record 450includes a Voice field 456 having a value false (F) that indicates voiceservices are not to be prescribed via the cellular network for thetelephony device associated with dummy record 450. An SMS field 458, onthe other hand, indicates SMS services are authorized for the telephonydevice for which dummy HLR record 450 is allocated. Thus, in the presentexample, HLR record 450 indicates SMS services are authorized for thetelephony device specified by MSISDN field 454. Various fields 460-468may be nulled. An MSC_ID field 470 may be assigned a value to redirectservices associated with HLR dummy record 450 to an enterprise entity inaccordance with an embodiment. In the present example, MSC_ID field 470is assigned Point Code_(A)—the SS7 point code of GS-C 180 such thatsignaling normally directed to a MSC is instead directed to the GS-Cthat services the enterprise network of the land-line telephony devicefor which dummy HLR record 450 is allocated. In accordance withembodiments, SMS messages directed to the telephony device specified byMSISDN field 454 are ultimately routed to a cellular telephony deviceassociated with HLR record 450 as will be described more fullyhereinbelow.

FIG. 5 is a simplified diagrammatic representation of an exemplary SMSmessage 500 format implemented in accordance with an embodiment. SMSmessage 500 may include a Sender_Num field 502 that includes the MSISDNof a mobile terminal that originates SMS message 500. Likewise, SMSmessage 500 may include a Destination_Num field 504 that includes theMSISDN of the destination mobile terminal to which SMS message 500 isdirected. Alternatively, the Destination_Num field may be included in aheader or may be included in fields or subfields included in SMS message500 that are not depicted. A message field 506 may include the SMSmessage content. Various other fields, such as fields that specify thelength of SMSC information, type of SMSC address, service center number,data coding scheme, timestamp, and various other information, may, andtypically are, included in SMS message 500 as is understood. Thedepicted representation of SMS message 500 is simplified to facilitatean understanding of embodiments disclosed herein.

In accordance with embodiments, the phone numbers specified bySender_Num field may be changed in transit of SMS message 500 tofacilitate one number servicing of multiple telephony devices. Forinstance, for a subscriber that is to be provided with one numberservicing, the subscriber may originate an SMS message from a mobileterminal assigned to the subscriber, and the sender number of theSender_Num field 502 may be replaced with a land-line enterprisedirectory number of a land-line telephony device assigned to the userprior to delivery of the SMS message to the destination device. In thismanner, the user receiving the SMS message is presented with theland-line phone number of the originator in the SMS message. In asimilar manner, when an SMS message is directed towards a user that isprovided with one number servicing, an enterprise directory number of aland-line telephone assigned to the user may be entered by anoriginating party as the destination number to which the SMS message isdirected. The destination number comprising a land-line phone number maybe changed in transit of the SMS message to a MSISDN number assigned tothe destination user such that the SMS message is routed to the mobileterminal of the destination user. In this manner, a person originatingan SMS message to a destination user that is provided with one numberservicing need only be aware of the destination user's land-lineenterprise directory number.

FIG. 6A is a diagrammatic representation depicting a signaling flow 600of an SMS transmission in a network generally configured as depicted anddescribed with reference to FIG. 2 from a mobile terminal user toanother mobile terminal user implementing one number servicing inaccordance with an embodiment. The network may include cellular networks110 and 111 and an enterprise network 150. In an embodiment, one numberservicing functionality provided in the system depicted in FIG. 6A maybe implemented using CAMEL Phase 3 triggers for Short Message Service,although other trigger mechanisms may be suitably substituted therefor.

In the following example, assume Party A and Party B are mobilesubscribers that are members of an Enterprise hosting enterprise network150 and that are assigned respective mobile terminals 140 and 141. PartyA's mobile number is +1-972-444-1001, and Party A's office number forland-line telephony device 154 deployed in enterprise network 150 is +1972-555-2001. Further assume Party A's short code, or office extension,is 2001. Party B's mobile terminal 141 number is +1-972-444-1002, PartyB's office number for land-line telephony device 155 deployed inenterprise network 150 is +1-972-555-2002, and Party B's short code is2002.

In a first example, Party A desires to send a SMS message to Party B.Party A can address the SMS message to either Party B's mobile number,office number, or short code. For purposes of illustration, assume PartyA enters Party B's office number as the SMS destination number.Accordingly, an SMS message 610 is generated at mobile terminal 140 asgenerally depicted in FIG. 6B. SMS message 610 may include a Sender_Numfield 612 assigned the MSISDN of mobile terminal 140, a Destination_Numfield 614 assigned the enterprise directory number of Party B'sland-line telephony device 155, and the SMS message content(illustratively designated “Message₁”) in a Message field 616 asdepicted in FIG. 6B. When Party B receives the SMS message, theoriginator's address will display as Party A's office number or shortcode in accordance with one number servicing implemented in accordancewith an embodiment.

SMS message 610 as depicted in FIG. 6B is entered at mobile terminal 140and is sent from Party A's mobile terminal 140 to a serving MSC 122(step 650). MSC 122 includes or interfaces with a VLR 124 that haspreviously downloaded Party A's subscriber profile from the HLR to whichParty A's mobile terminal 140 is registered as is understood. As thenetwork supports CAMEL Phase 3, the Short Message Service CAMELSubscription Information (SMS-CSI) is transferred to VLR 124. TheSMS-CSI contains trigger information which is required to invoke CAMELService Logic for Mobile Originating Short Message submissions. In thiscase, MSC 122 will trigger to GS-C 180 which will act as the SMSC (step651).

After the trigger is launched to the GS-C 180, GS-C 180 identifies theenterprise to which Party A belongs, and subsequently sends SMS message610 to corresponding GS-E 182 (step 652). GS-E 182 verifies if thedestination address of SMS message 610 is a member of Enterprise X byinterrogating an Enterprise Member profile database 190. EnterpriseMember profile database 190 may include records or profiles forrespective enterprise members that associate a land-line number of anenterprise telephony device assigned to a particular enterprise memberwith a MSISDN number of a mobile terminal assigned to the enterprisemember as described with reference to FIG. 2. In the present example,Party A has entered Party B's land-line number as the destination numberof SMS message 610. Interrogation of profile database 190 with Party B'sland-line number results in selection of a record 190 b allocated forParty B that indicates the destination number is Party B's land-line andprovides the MSISDN of Party B's mobile terminal 141 to GS-E 182. GS-E182 may then modify the destination address of SMS message 610 to be thecorresponding mobile number of Party B as depicted by SMS message 610 inFIG. 6C having a Destination_Num field 614 with the MSISDN of mobileterminal 141. This enables the message to be routed through the mobilenetwork to the destination party.

In addition, the GS-E 182 retrieves the member record 190 a assigned toParty A by interrogating Enterprise Member profile database 190 withParty A's mobile terminal number retrieved from Sender_Num field 612 ofSMS message 610. Party A's member record 910 a includes Party A'sland-line number in association with Party A's mobile terminal MSISDN ordirectory number. Accordingly, GS-E 182 may modify the source address tobe Party A's office number or short code in place of Party A's mobilenumber such that the recipient will receive the SMS with Party A'soffice number as the originator as depicted by Sender_Num field 612 ofSMS message 610 in FIG. 6C.

In accordance with another embodiment, GS-E 182 may, upon determiningthe destination subscriber is a member of Enterprise X, invoke anenterprise messaging service, such as a corporate Instant Messagingservice, for delivery of SMS message 610. For example, the member recordfor Party B retrieved from member database 190 may indicate that SMSmessages are to be additionally delivered to Party B via an InstantMessaging service. Assuming the SMS message is to be additionallydelivered to Party B via an Instant Messaging service, GS-E 182 mayconvert the SMS message to an Instant Message and send the IM to anEnterprise IM server 192 (step 654). The IM may then be forwarded toParty B, e.g., to Party B's enterprise desktop 153 (step 655). Inaddition, GS-E 182 may record the transaction as part of Party A's logswithin the enterprise.

Delivery of SMS message 610 to Party B's mobile terminal 141 maycontinue with GS-E 182 responding to GS-C 180 (step 656), which in turnresponds to the MSC 122 trigger with the instructions to route themessage to SMSC 144 for delivery (step 657). MSC 122, in turn, forwardsthe SMS message to SMSC 144 for delivery to Party B (step 658). SMSC 144then queries HLR 126 to determine the serving MSC 123 of the recipientbased on the recipient's mobile number (step 659). HLR 126 responds toSMSC 144 with the serving MSC of the recipient (step 660). SMSC 144 willthen deliver the message with the modifications made by GS-E 182 to MSC123 (step 661) which delivers the SMS to mobile terminal 141 via anappropriate base station sub-system (step 662). The source address willbe Party A's office number or short code, and the destination addresswill be Party B's mobile number as depicted in FIG. 6C.

FIG. 7A is a diagrammatic representation depicting a signaling flow 700of an SMS transmission in a network generally configured as depicted anddescribed with reference to FIG. 2 from a mobile terminal user toanother mobile terminal user implementing one number servicing inaccordance with an embodiment. The network may include cellular networks110 and 111 and an enterprise network 150.

As in the example depicted in FIG. 6A, Party A desires to send an SMSmessage to Party B, and for purposes of illustration assume Party Aenters Party B's office number as the SMS destination number.Accordingly, an SMS message 710 is generated at mobile terminal 140 asgenerally depicted in FIG. 7B. SMS message 710 may include a Sender_Numfield 712 assigned the MSISDN of mobile terminal 140, a Destination_Numfield 714 assigned the enterprise directory number of Party B'sland-line telephony device 155, and the SMS message content(illustratively designated “Message₂”) in a Message field 716 asdepicted in FIG. 7B.

In the present example, however, assume the network does not supportCAMEL Phase 3 triggers. Instead, a Transparent Router 770 is placed infront of SMSC 144 and monitors the link for SMS messages originated bysubscribers of the enterprise service. Subscriber A may originate SMSmessage 710 addressed to Subscriber B (step 750) that is transmitted toserving MSC 122 which attempts to forward the SMS to SMSC 144 (step751). However, transparent router 770 detects the SMS message andevaluates whether the originator subscribes to the enterprise service.If the originator is not subscribed to the enterprise service,transparent router 770 may allow the message to pass through unmodified.Assuming Subscriber A is subscribed to the enterprise service,transparent router 770 intercepts the message and re-routes it to GS-C180 (step 752) which forward SMS message 710 to GS-E 182 (step 753).GS-E 182 verifies if the destination address of the SMS message is amember of Enterprise X by interrogating an Enterprise Member profiledatabase 190. In the present example, Party B, the destination party, isa member of Enterprise X. Assume Party A entered Party B's land-linenumber as the destination number of the SMS message. Interrogation ofprofile database 190 with Party B's land-line number results inselection of record 190 b that indicates the destination number is PartyB's land-line and provides the MSISDN of Party B's mobile terminal 141to GS-E 182. GS-E 182 may then modify the destination address of the SMSmessage to be the corresponding mobile number of Party B as depicted byDestination_Num field 714 of SMS message 710 in FIG. 7C. This enablesthe message to be routed through the mobile network to the destinationparty.

In addition, GS-E 182 retrieves member record 190 a assigned to Party Awhich includes Party A's land-line number. Accordingly, GS-E 182 maymodify the source address to be Party A's office number or short code inplace of Party A's mobile number such that the recipient will receivethe SMS with Party A's office number as the originator as depicted bySender_Num field 712 in FIG. 7C.

In accordance with another embodiment, GS-E 182 may, upon determiningthe destination subscriber is a member of Enterprise X, invoke anenterprise messaging service, such as a corporate Instant Messagingservice, for delivery of the SMS message. For example, member record 190b for Party B retrieved from member database 190 may indicate that SMSmessages are to be additionally delivered to Party B via an InstantMessaging service. Assuming the SMS message is to be additionallydelivered to Party B via an Instant Messaging service, GS-E 182 mayconvert the SMS to an Instant Message and send the IM to an EnterpriseIM server 192 (step 754). The IM may then be forwarded to Party B, e.g.,to Party B's enterprise desktop 153 (step 755). In addition, GS-E 182may record the transaction as part of Party A's logs within theenterprise.

Delivery of the SMS message to Party B's mobile terminal 141 maycontinue with GS-E 182 responding to GS-C 180 by returning the SMSmessage to be re-injected to GS-C 180 (step 756) with the modificationsperformed by GS-E 182 as depicted in FIG. 7C which forwards the SMSmessage to transparent router 770 (step 757). Transparent router 770, inturn, forwards the SMS message to SMSC 144 (step 758). SMSC 144 thenqueries HLR 126 to determine the serving MSC 123 of the recipient basedon the recipient's mobile number (step 759). HLR 126 responds to SMSC144 with the serving MSC 123 of the recipient (step 760). SMSC 144 willthen deliver the message with the modifications made by GS-E 182 to MSC123 (step 761) which delivers the SMS to mobile terminal 141 via anappropriate base station sub-system (step 762). The source address willbe Party A's office number or short code, and the destination addresswill be Party B's mobile number as depicted in FIG. 7C.

FIG. 8A is a diagrammatic representation depicting a signaling flow 800of an SMS transmission in a network 100 generally configured as depictedand described with reference to FIG. 2 from a mobile terminal user toanother mobile terminal user implementing one number servicing inaccordance with an embodiment. The network may include cellular networks110 and 111 and an enterprise network 150.

As in the example depicted in FIG. 7A, Party A desires to send a SMSmessage to Party B, and for purposes of illustration assume Party Aenters Party B's office number as the SMS destination number.Accordingly, an SMS message 810 is generated at mobile terminal 140 asgenerally depicted in FIG. 8B. SMS message 810 may include a Sender_Numfield 812 assigned the MSISDN of mobile terminal 140, a Destination_Numfield 814 assigned the enterprise directory number of Party B'sland-line telephony device 155, and the SMS message content(illustratively designated “Message₃”) in a Message field 816 asdepicted in FIG. 8B.

In the present example, however, a Transparent Router 870 is used onlyto intercept and re-route short messages originated by subscribers ofthe enterprise service, but is not used to re-inject the message onceprocessed by the GS-E.

Subscriber A may originate SMS message 810 addressed to Subscriber B(step 850) that is transmitted to serving MSC 122 which attempts toforward the SMS to SMSC 144 (step 851). However, transparent router 870detects SMS message 810 and evaluates whether the originator subscribesto the enterprise service. If the originator is not subscribed to theenterprise service, transparent router 870 may allow the message to passthrough unmodified. Assuming Subscriber A is subscribed to theenterprise service, transparent router 870 intercepts the message andre-routes it to GS-C 180 (step 852) which forwards SMS message 810 toGS-E 182 (step 853). GS-E 182 verifies the destination address of SMSmessage 810 is a member of Enterprise X by interrogating EnterpriseMember profile database 190. In the present example, Party B, thedestination party, is a member of Enterprise X. Assume Party A enteredParty B's land-line number as the destination number of SMS message 810.Interrogation of profile database 190 results in selection of record 190b that indicates the destination number is Party B's land-line numberand provides the MSISDN of Party B's mobile terminal 141 to GS-E 182.GS-E 182 may then modify the destination address of the SMS message tobe the corresponding mobile number of Party B as depicted byDestination_Num field 814 in FIG. 8C. This enables the message to berouted through the mobile network to the destination party.

In addition, GS-E 182 retrieves member record 190 a assigned to Party Awhich includes Party A's land-line number. Accordingly, GS-E 182 maymodify the source address to be Party A's office number or short code inplace of Party A's mobile number such that the recipient will receivethe SMS message with Party A's office number as the originator asdepicted by the Sender_Num field 812 in FIG. 8C.

In accordance with another embodiment, GS-E 182 may, upon determiningthe destination subscriber is a member of Enterprise X, invoke anenterprise message service, such as a corporate Instant Messagingservice, for delivery of the SMS message. For example, member record 190b for Party B retrieved from member database 190 may indicate that SMSmessages are to be additionally delivered to Party B via an InstantMessaging service. Assuming the SMS message is to be additionallydelivered to Party B via an Instant Messaging service, GS-E 182 mayconvert the SMS to an Instant Message and send the IM to an EnterpriseIM server 192 (step 854). The IM may then be forwarded to Party B, e.g.,to Party B's enterprise desktop 153 (step 855). In addition, GS-E 182may record the transaction as part of Party A's logs within theenterprise.

Delivery of SMS message 810 to Party B's mobile terminal 141 maycontinue with GS-E 182 responding to GS-C 180 by returning SMS message810 to be re-injected to GS-C 180 (step 856) with the modificationsperformed by GS-E 182 as depicted by SMS message 810 in FIG. 8C. GS-C180 may then forward the SMS message to SMSC 144 (step 857), rather thanthe transparent router as performed in the configuration depicted inFIG. 7A, with the modified information. In this instance, GS-C 180 isadapted to handle any response from SMSC 144 resulting from transmissionof the SMS message thereto. SMSC 144 then queries HLR 126 to determinethe serving MSC 123 of the recipient based on the recipient's mobilenumber (step 858). HLR 126 responds to SMSC 144 with the serving MSC ofthe recipient (step 859). SMSC 144 will then deliver the message withthe modifications made by GS-E 182 to MSC 123 (step 860) which deliversthe SMS to mobile terminal 141 via an appropriate base stationsub-system (step 861). The source address will be Party A's officenumber or short code, and the destination address will be Party B'smobile number as depicted in FIG. 8C.

FIG. 9A is a diagrammatic representation depicting a signaling flow 900of an SMS transmission in a network system from a mobile terminal userto another mobile terminal user implementing one number servicing inaccordance with an embodiment. The network system may include cellularnetworks 110 and 111 and an enterprise network 150.

In the following example, assume Party C and Party A are mobilesubscribers, Party C is not a member of the Enterprise hostingenterprise network 150, and that Party A is a member of the Enterprisehosting enterprise network 150. Further assume Party C and Party A areassigned respective mobile terminals 142 and 140. Party A's mobilenumber is +1-972-444-1001, Party A's office number is +1 972-555-2001,and Party A's short code is 2001. Party C's mobile number is+1-214-777-7777.

The non-enterprise subscriber may originate an SMS to the office numberof the enterprise user at mobile terminal 142. Accordingly, an SMSmessage 910 is generated at mobile terminal 142 as generally depicted inFIG. 9B. SMS message 910 may include a Sender_Num field 912 assigned theMSISDN of mobile terminal 142, a Destination_Num field 914 assigned theenterprise directory number of Party A's land-line telephony device 154,and the SMS message content (illustratively designated “Message₄”) in aMessage field 916 as depicted in FIG. 9B. The SMS message is sent frommobile terminal 142 to servicing MSC 122 (step 950). MSC 122 includes orinterfaces with a VLR 124 that has previously downloaded Party C'ssubscriber profile from the HLR to which Party C's mobile terminal 142is registered as is understood. In this case, MSC 122 identifies SMSC144 as the servicing SMSC and forwards the SMS message thereto (step951.)

SMSC 144 may then query HLR 126 based on the office number entered byParty C as the destination to identify the serving MSC (step 952). Priorto this, HLR 126 will have been provisioned with a standalone, or dummy,subscriber profile for the enterprise user's office number similar todummy HLR record 450 depicted and described with reference to FIG. 4B.Dummy record 450 will indicate Party A associated with the destinationoffice number has SMS service. In addition, prior to these events, GS-C180 will register with HLR 126 as the serving MSC of the enterprisesubscriber in the HLR dummy profile associated with the office number.For instance, assume dummy HLR record 450 depicted in FIG. 4B isallocated for Subscriber A's land-line office telephony device 154. Inthis instance, GS-C 180 may be registered as the serving MSC of theland-line telephony device assigned to Party A by assigning the pointcode (illustratively designated Point Code_(A)) of GS-C 180 to theMSC_ID field 440 of dummy HLR record 450. The HLR profile associatedwith the enterprise subscriber's office number will be supportedthroughout mobile networks such that any MSC can query the HLR for theprofile. Note that this HLR profile is entirely separate from theexisting HLR profile associated with the enterprise subscriber's mobilenumber, i.e., HLR record 400. The handling of voice calls to the officenumber from mobile networks will be described in a subsequent section.

HLR 126 responds with the serving MSC being the GS-C 180 which hadpreviously registered as the serving MSC (step 953). SMSC 144 may thensend the SMS message to GS-C 180 accordingly (step 954). GS-C 180identifies the enterprise to which the destination number (SubscriberA's land-line office number) belongs and routes SMS message 910 tocorresponding GS-E 182 (step 955). GS-E 182 may modify the destinationnumber to be the mobile number of the enterprise user, that is to themobile number of mobile terminal 140, in order to enable the message tobe routed through the mobile network as depicted by Destination_Numfield 914 in FIG. 9C.

In accordance with another embodiment, GS-E 182, upon determining thedestination subscriber is a member of Enterprise X, may invoke anenterprise message service, such as a corporate Instant Messagingservice, for delivery of the SMS message. For example, the member record190 a for Party A retrieved from member database 190 may indicate thatSMS messages are to be additionally delivered to Party A via an InstantMessaging service. Assuming the SMS message is to be additionallydelivered to Party A via an Instant Messaging service, GS-E 182 mayconvert the SMS to an Instant Message and send the IM to an EnterpriseIM server 192 (step 956). The IM may then be forwarded to Party A, e.g.,to Party A's enterprise desktop 152 (step 957). In addition, GS-E 182may record the transaction as part of Party A's logs within theenterprise.

Delivery of the SMS message to Party A's mobile terminal 140 maycontinue by GS-E 182 responding to GS-C 180 with the SMS message havingthe modified destination information (step 958). GS-C 180 may thenoriginate an SMS message to SMSC 144 with the modified destinationinformation as depicted in FIG. 9C (step 959).

SMSC 144 may then query HLR 126 based on the destination mobile number(step 960), and HLR 126 may respond with the serving MSC 123 of theenterprise user's mobile terminal 140 (step 961). SMSC 144 may thendeliver the SMS message to MSC 123 and to the destination mobileterminal 140 (step 962).

FIG. 10 is a diagrammatic representation depicting a signaling flow 1000for handling of mobile originations for voice calls to an enterprisenumber which is provisioned in a mobile network HLR in accordance withan embodiment. This implementation enables voice calls originated in themobile network to be routed out to the public land-line network in orderto reach the office number destination in the land-line network.

In the following example, assume Party C is a mobile subscriber, andthat Party A is a member of the Enterprise hosting enterprise network150. Further assume Party C is assigned mobile terminal 142, and Party Ais assigned office land-line telephony device 154. In this instance,assume Party A has a dummy HLR record similar to dummy HLR record 450allocated in the HLR for land-line telephony device 154 to facilitatedelivery (to Party A's mobile terminal 140) of SMS messages submittedwith the enterprise directory number of device 154 as the destinationnumber as described above.

A call may be originated by Party C at mobile terminal 142 to the officenumber of device 154 assigned to Party A (step 1050). As noted above,Party A has a profile in HLR 126 for the office number of device 154 forthe purpose of enabling SMS messages submitted with the office number asthe destination number.

MSC 122, on receipt of the call setup request, queries HLR 126 for arouting number to the serving MSC in order to deliver the call to therecipient (step 1051). HLR queries GS-C 180 that has previouslyregistered as the serving MSC for the office number (step 1052). GS-C180 is responsible for maintaining the periodic registrations such thatthe HLR profile continuously points to GS-C 180 as the serving MSC.

GS-C 180 identifies the enterprise network associated with the officenumber destination and sends the message to the corresponding GS-E (step1053). GS-E 182 sets the routing number to be returned to theoriginating MSC to be the office number on the public network. GS-E 182may also communicate with another enterprise messaging service (step1054) to convey an incoming call to a user terminal (step 1055). Inaddition, GS-E 182 may record the transaction as part of Party A's logswithin the enterprise.

GS-E 182 may then respond to GS-C 180 (step 1056) which in turn respondsto HLR 126 (step 1057). HLR 126 then may respond to serving MSC 122 withthe routing number to the serving MSC set to the office number on thepublic land-line network (step 1058).

With this information, originating MSC 122 routes the call to therouting number. The call is routed out to the public network 1065 to theoffice number which could be in the enterprise PBX 158 (step 1059). Inthis case, enterprise PBX 158 may route the call to the office number oftelephony device 154 assigned to the subscriber (step 1060).

FIG. 11 is a flowchart of exemplary SMS message processing as may beimplemented by an enterprise gateway server that facilitates one numberservice in accordance with an embodiment. The SMS message processingroutine is invoked (step 1102), and the gateway server awaits receipt ofan SMS message (step 1104). On receipt of an SMS message, the sendernumber and the destination number may be read from the SMS message (step1106), e.g., from respective sender number and destination number fields502 and 504. An evaluation may then be made to determine if thedestination is assigned to an enterprise member (step 1108), e.g., byinterrogation of enterprise member database 190 with the destinationnumber read from the SMS message. In the event that the destinationnumber is not assigned to an enterprise member, the SMS messageprocessing routine may proceed to evaluate whether the sender number isassigned to an enterprise member (step 1114).

Returning again to step 1108, in the event that the destination numberis evaluated as being assigned to an enterprise member, an evaluationmay then be made to determine if the destination number is a land-linenumber assigned to the destination party (step 1110). In the event thatthe destination number is evaluated as comprising a land-line number,the processing routine may proceed to evaluate the sender numberaccording to step 1114. In the event that the destination number isevaluated as a land-line number of a telephony device assigned to thedestination party, the destination number of the SMS message may bereplaced with the mobile, or MSISDN, number of the mobile terminalassigned to the destination party (step 1112). The SMS messageprocessing routine may then continue to step 1114 to evaluate the sendernumber of the SMS message.

In the event that the sender number is not determined to be assigned toan enterprise member at step 1114, the SMS message processing routinemay proceed to continue with routing of the SMS message (step 1120).Alternatively, if the sender number is determined to be assigned to anenterprise member at step 1114, the SMS processing routine may thenevaluate whether the sender number is a mobile number of the mobileterminal assigned to the sending party (step 1116). In the event thatthe sender number is not evaluated as comprising a mobile number, theSMS message may be routed according to step 1120. If, however, thesender number is evaluated as comprising a mobile number of a mobileterminal assigned to the sending party, the sender number may bereplaced with the land-line number assigned to the sending party (step1118), and the gateway server may then continue with routing of the SMSmessage according to step 1120. The SMS message processing routine cyclemay then end (step 1122).

FIG. 12 is a diagrammatic representation depicting a signaling flow 1200for handling of mobile originations for voice calls to an enterprisenumber which is provisioned in a mobile network HLR in accordance withan embodiment. This implementation enables voice calls originated in themobile network to an enterprise number be automatically re-routed basedon criteria in the GS-C and/or GS-E to the corresponding mobile numberin the mobile network in order to reach the mobile subscriber associatedwith the enterprise number. As an example, this function may be used inan emergency situation when landline network connections to theenterprise are inoperable. In this case the GS-C and/or GS-E may beplaced in an emergency routing mode such that mobile originated calls toenterprise numbers will instead be routed to their mobile devices.

In the following example, assume Party C is a mobile subscriber, andthat Party A is a member of the Enterprise hosting enterprise network150. Further assume Party C is assigned mobile terminal 142, and Party Ais assigned office land line telephony device 154. In this instance,assume Party A has a dummy HLR record similar to dummy HLR record 450allocated in HLR 126 for land line telephony device 154 to facilitatedelivery (to Party A's mobile terminal 140) of SMS messages submittedwith the enterprise directory number of device 154 as the destinationnumber.

A call may be originated by Party C at mobile terminal 142 to the officenumber of device 154 assigned to Party A (step 1250). As noted above,Party A has a profile in HLR 126 for the office number of device 154 forthe purpose of enabling SMS messages submitted with the office number asthe destination number.

MSC 122, on receipt of the call setup request, queries HLR 126 for arouting number to the serving MSC in order to deliver the call to therecipient (step 1252). HLR queries GS-C 180 that has previouslyregistered as the serving MSC for the office number (step 1254). GS-C180 is responsible for maintaining the periodic registrations such thatthe HLR profile continuously points to GS-C 180 as the serving MSC.

GS-C 180 identifies the enterprise network associated with the officenumber destination and sends the message to the corresponding GS-E 182(step 1256).

GS-E 182 sets the routing number to be returned to the originating MSCto be the corresponding mobile number of enterprise user Party A. Notethat if GS-E 182 is not available, GS-C 180 may set the routing numberto be returned to the originating MSC 122 to be the corresponding mobilenumber of the enterprise user Party A.

GS-E 182 may also communicate with another enterprise messaging service(step 1258) to convey an incoming call to user terminal 152 (step 1260).In addition, GS-E 182 may record the transaction as part of Party A'slogs within the enterprise.

GS-E 182 may then respond to GS-C 180 (step 1262) which in turn respondsto HLR 126 (step 1264). HLR 126 then may respond to serving MSC 122 withthe routing number to the serving MSC set to the mobile number to berouted out to the public landline network (step 1266). If both Party Cand Party A are subscribers on the same mobile operator network, thecall would instead be routed directly from the MSC serving Party C tothe GMSC in the same network of which Party A is a subscriber. Otherwisethe call is routed out to the public network as described below.

The call is then routed via the public network (step 1268) to theGateway MSC (GMSC) 124 of the network to which the mobile subscribersubscribes (step 1270). GMSC 124 responds to PSTN 1165 (step 1272) whichin turn responds to MSC 122 (step 1274) after which the originating callleg is through-connected from the Party C, i.e., mobile terminal 142, tothe GMSC 124.

GMSC 124 then queries HLR 126 (step 1276) to obtain a routing to theserving MSC of Party A. HLR 126 requests a routing number from servingMSC 123 (step 1278) which is returned to HLR 126 (step 1280). HLR 126returns the routing number to GMSC 123 (step 1282). GMSC 123 then routesthe call to the routing number over the public landline network 1165(step 1284) to serving MSC 123 (step 1286). Serving MSC 124 responds(step 1288) to the public landline network 1165 which in turn respondsto GMSC 124 (step 1290). The terminating call leg is through-connectedto the serving MSC (step 1292).

As described, embodiments disclosed herein provide mechanisms forenabling the use of an alternative numbering plan for delivering shortmessages to mobile subscribers. Enterprise members or other userssubscribed to a one number service may send short messages destined tomembers of an enterprise or closed network from their mobile or otherdevices associated with their subscription using an alternativeenterprise directory number. The alternative enterprise directory numbermay comprise an office number of a land-line telephony device. Thealternative enterprise directory number, rather than the mobile number,will be presented at the destination device as the originating number.The recipient can respond to the message by addressing the response tothe enterprise or closed network number, and the SMS message will bedelivered to the originator's mobile or other devices associated withtheir subscription.

Although the specific network architecture and nomenclature are depictedand described according to the GSM, it is understood that this is doneso for illustrative purposes only and that the network architecture onwhich embodiments disclosed herein may be applied is not limited to anyparticular standard, but rather may be equivalently implemented on anyother communications system supporting any variety of cellularcommunication systems, e.g. D-AMPS, GSM, CDMA, IS-41, ANSI-41, UMTS,etc.

The flowchart of FIG. 11 depicts process serialization to facilitate anunderstanding of disclosed embodiments and is not necessarily indicativeof the serialization of the operations being performed. In variousembodiments, the processing steps described in FIG. 11 may be performedin varying order, and one or more depicted steps may be performed inparallel with other steps. Additionally, execution of some processingsteps of FIG. 11 may be excluded without departing from embodimentsdisclosed herein.

The illustrative block diagrams and flowcharts depict process steps orblocks that may represent modules, segments, or portions of code thatinclude one or more executable instructions for implementing specificlogical functions or steps in the process. Although the particularexamples illustrate specific process steps or procedures, manyalternative implementations are possible and may be made by simpledesign choice. Some process steps may be executed in different orderfrom the specific description herein based on, for example,considerations of function, purpose, conformance to standard, legacystructure, user interface design, and the like.

Aspects of the present invention may be implemented in software,hardware, firmware, or a combination thereof. The various elements ofthe system, either individually or in combination, may be implemented asa computer program product tangibly embodied in a machine-readablestorage device for execution by a processing unit. Various steps ofembodiments of the invention may be performed by a computer processorexecuting a program tangibly embodied on a computer-readable medium toperform functions by operating on input and generating output. Thecomputer-readable medium may be, for example, a memory, a transportablemedium such as a compact disk, a floppy disk, or a diskette, such that acomputer program embodying the aspects of the present invention can beloaded onto a computer. The computer program is not limited to anyparticular embodiment, and may, for example, be implemented in anoperating system, application program, foreground or background process,driver, network stack, or any combination thereof, executing on a singlecomputer processor or multiple computer processors. Additionally,various steps of embodiments of the invention may provide one or moredata structures generated, produced, received, or otherwise implementedon a computer-readable medium, such as a memory.

Although embodiments of the present disclosure have been described indetail, those skilled in the art should understand that they may makevarious changes, substitutions and alterations herein without departingfrom the spirit and scope of the present disclosure.

What is claimed is:
 1. A method, comprising: verifying, at an enterprisenetwork, a destination address of a message is associated with adestination; invoking an enterprise messaging service to deliver themessage based on message routing instructions; modifying at least oneof: the destination address of the message to include a mobile telephonenumber associated with the destination device, and an originationaddress of the message to include an enterprise telephone numberassociated with a mobile device; and routing the message to thedestination device.
 2. The method of claim 1, further comprisingdetermining whether the mobile device is subscribed to the enterprisenetwork.
 3. The method of claim 2, wherein upon determining that themobile device is not subscribed to the enterprise network, forwardingthe message without modification on a communication link via a router.4. The method of claim 2, wherein upon determining the mobile device issubscribed to the enterprise network, intercepting the message via arouter and re-routing the message to a gateway server in a carriernetwork.
 5. The method of claim 1, further comprising monitoring acommunication link via a router for the message originated by the mobiledevice.
 6. The method of claim 5, further comprising intercepting themessage via the router and determining whether to forward the message onthe communication link.
 7. The method of claim 6, further comprisingdetermining whether to re-route the message via another communicationlink based on an enterprise network subscription status of the mobiledevice.
 8. An apparatus, comprising: a transmitter configured to forwarda message; and a processor configured to monitor a communication linkfor the message; wherein the transmitter is further configured totransmit the message to a gateway server in an enterprise network, whichverifies a destination address of the message is associated with adestination device via retrieving an enterprise profile recordassociated with the destination device, and wherein the processor isfurther configured to modify the destination address of the message toinclude a mobile address associated with the destination device, whereinthe message is routed to the mobile address.
 9. The apparatus of claim8, wherein the processor is further configured to determine whether themobile device is subscribed to the enterprise network.
 10. The apparatusof claim 8, wherein upon a determination that the mobile device is notsubscribed to the enterprise network, the transmitter is configured toforward the message without modification on the communication link. 11.The apparatus of claim 8, wherein the processor is further configured tointercept the message, and determine whether to forward the message viathe transmitter on the communication link.
 12. The apparatus of claim11, wherein the processor is further configured to re-route the messagevia another communication link based on an enterprise networksubscription status of the mobile device.
 13. The apparatus of claim 8,wherein the processor modifies an origination address of the message toinclude an enterprise address associated with the mobile device.
 14. Theapparatus of claim 8, wherein upon determining the destination addressis associated with the destination device that is a member of theenterprise network, the processor invokes an enterprise messagingservice to deliver the message based on message routing instructions inthe enterprise profile record.
 15. A non-transitory computer readablestorage medium configured to store instructions that when executed causea processor to perform: receiving a message at a gateway server in anenterprise network; verifying a destination address of the message isassociated with a destination device via retrieving an enterpriseprofile record associated with the destination device; modifying thedestination address of the message to include a mobile addressassociated with the destination device; and routing the message to themobile address.
 16. The non-transitory computer readable storage mediumof claim 15, wherein the processor is further configured to performdetermining whether the mobile device is subscribed to the enterprisenetwork.
 17. The non-transitory computer readable storage medium ofclaim 16, wherein upon determining that the mobile device is notsubscribed to the enterprise network, forwarding the message withoutmodification on a communication link via a router.
 18. Thenon-transitory computer readable storage medium of claim 16, whereinupon determining the mobile is subscribed to the enterprise network,intercepting the message via a router and re-routing the message to agateway server in a carrier network.
 19. The non-transitory computerreadable storage medium of claim 15, wherein the processor is furtherconfigured to perform: monitoring a communication link via a router fora message originated by a mobile device intercepting the message via therouter and determining whether to forward the message on thecommunication link or re-route the message via another communicationlink based on an enterprise network subscription status of the mobiledevice.
 20. The non-transitory computer readable storage medium of claim15, wherein the processor is further configured to perform modifying anorigination address of the message to include an enterprise addressassociated with the mobile device, and wherein upon determining thedestination address is associated with the destination device, invokingan enterprise messaging service to deliver the message based on messagerouting instructions in the enterprise profile record.